Triple
T24073579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General_Category |
E596300
|
entity |
| Predicate | representedInFile |
P103
|
FINISHED |
| Object | UnicodeData.txt |
—
|
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: UnicodeData.txt | Statement: [General_Category, representedInFile, UnicodeData.txt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedInFile Context triple: [General_Category, representedInFile, UnicodeData.txt]
-
A.
representedInFinal
Indicates that something appears or is included in its completed or final version or outcome.
-
B.
representedInPartBy
Indicates that something is partially depicted, expressed, or captured within another thing, but not in its entirety.
-
C.
hasRepresentationIn
chosen
Indicates that one entity is represented, depicted, or encoded within another entity, such as a concept, object, or data structure having a corresponding representation in a specific medium or context.
-
D.
representedInTitle
Indicates that an entity is mentioned or reflected in the title of another resource.
-
E.
isRepresentedOn
Indicates that something serves as a visual, symbolic, or formal depiction of something else on a particular medium or surface.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db1bb98081909f56cd7a06dba054 |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:42 p.m.