Triple
T7423301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDF 1.1 N-Quads |
E171300
|
entity |
| Predicate | graphComponent |
P69700
|
FINISHED |
| Object | subject |
—
|
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: subject | Statement: [RDF 1.1 N-Quads, graphComponent, subject]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphComponent Context triple: [RDF 1.1 N-Quads, graphComponent, subject]
-
A.
graphics
Indicates a relationship where one entity is responsible for creating, providing, or handling visual representations or graphical content for another entity or context.
-
B.
graphAnalogue
chosen
Indicates that one entity serves as a graph-theoretic counterpart or structural analogue of another entity.
-
C.
plotElement
Indicates that one entity functions as a narrative component or structural element within the storyline of another entity (such as a work of fiction or media).
-
D.
coreFigure
Indicates that an entity serves as the central or most important figure within a given context, group, or structure.
-
E.
chartDepiction
Indicates that one entity is a chart that visually represents or depicts information about another entity.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2eece588190905774e7151edcb8 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.