Triple
T7423168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N-Triples |
E171297
|
entity |
| Predicate | serializationOf |
P55780
|
FINISHED |
| Object | RDF triples |
—
|
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: RDF triples | Statement: [N-Triples, serializationOf, RDF triples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serializationOf Context triple: [N-Triples, serializationOf, RDF triples]
-
A.
originalSerialization
Indicates that one entity is the initial or source serialized form from which another serialized representation is derived.
-
B.
serializedIn
Indicates that something is published or presented in sequential installments within a larger medium or series.
-
C.
serialized
chosen
Indicates that one entity has been converted into a sequential, storable or transmittable data format representing its structure or state.
-
D.
representationOrder
Indicates the sequence or hierarchy in which representations of entities are arranged or prioritized relative to one another.
-
E.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with 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.