Triple
T31131181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 12.0 |
E793510
|
entity |
| Predicate | hasPropertyDataFile |
P70988
|
FINISHED |
| Object | PropList.txt version 12.0.0 |
—
|
LITERAL FINISHED |
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: PropList.txt version 12.0.0 | Statement: [Unicode 12.0, hasPropertyDataFile, PropList.txt version 12.0.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPropertyDataFile Context triple: [Unicode 12.0, hasPropertyDataFile, PropList.txt version 12.0.0]
-
A.
hasDataFile
chosen
Indicates that an entity is associated with or linked to a specific data file that stores its related information.
-
B.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
C.
hasPropertyT
Indicates that an entity possesses or is characterized by a specific property T.
-
D.
hasConfigurationFile
Indicates that an entity is associated with or defined by a specific configuration file.
-
E.
hasPropertyType
Indicates that an entity possesses or is associated with a specific type or category of property.
- F. None of above.
Provenance (3 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0041860fd081908623ef9fd40a9775 |
completed | May 10, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_6a00414b01488190a312adb3b25d69cf |
completed | May 10, 2026, 8:26 a.m. |
Created at: April 29, 2026, 9:05 p.m.