Triple
T7423158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N-Triples |
E171297
|
entity |
| Predicate | syntaxElement |
P76879
|
FINISHED |
| Object | IRIs |
—
|
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: IRIs | Statement: [N-Triples, syntaxElement, IRIs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: syntaxElement Context triple: [N-Triples, syntaxElement, IRIs]
-
A.
structuralExpression
Indicates that one entity represents the structural or formal expression of another, such as a configuration, layout, or organized form that embodies its structure.
-
B.
syntaxBasedOn
Indicates that the syntactic structure or rules of one entity are derived from, influenced by, or constructed according to the syntax of another entity.
-
C.
typicalProgramElement
Indicates that one program element is a representative or characteristic example of another program element or category of elements.
-
D.
symbolType
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
E.
signatureElement
Indicates that one entity is a component or part of another entity’s signature, such as a defining element within a formal or identifying representation.
- 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_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. |
| PDg | Predicate description generation | batch_69c6f1ee5ab8819091082324f2dc3b8c |
completed | March 27, 2026, 9:09 p.m. |
Created at: March 27, 2026, 3:12 p.m.