Triple
T1491007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makers |
E29577
|
entity |
| Predicate | hasSerialization |
P28587
|
FINISHED |
| Object | online serialization |
—
|
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: online serialization | Statement: [Makers, hasSerialization, online serialization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSerialization Context triple: [Makers, hasSerialization, online serialization]
-
A.
hasOrdinalSeries
Indicates that one entity belongs to, or is positioned within, an ordered sequence or series relative to other entities.
-
B.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
C.
hasSignatureTrait
Indicates that an entity possesses a defining or characteristic trait that is especially distinctive or representative of it.
-
D.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
E.
hasPar
Indicates a relationship where one entity has another entity as its parent.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c3ace4819081bc2b86ee2486b6 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52c703c8190a56389b09d97659f |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8:12 p.m.