Triple
T27766669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hànshū |
E701618
|
entity |
| Predicate | compilerFamily |
P163953
|
FINISHED |
| Object | Ban family |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Ban family | Statement: [Hànshū, compilerFamily, Ban family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compilerFamily Context triple: [Hànshū, compilerFamily, Ban family]
-
A.
compilerType
Indicates the specific kind or category of compiler associated with or used by an entity.
-
B.
programmingLanguageFamily
Indicates that one programming language belongs to, or is categorized under, the family or lineage of another programming language.
-
C.
compilerLanguage
Indicates that one entity is the programming language in which a given compiler is implemented.
-
D.
compilerRelationship
Indicates a relationship where one entity functions as, produces, or is otherwise associated with the compiler used for another entity (such as software, code, or a build process).
-
E.
compilerOccupation
Indicates that one entity works as a compiler (e.g., of texts, data, or code) in relation to another entity, typically an organization, project, or work.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 4:31 p.m.