Triple
T27176466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sl(2,C) |
E683055
|
entity |
| Predicate | realForm |
P161817
|
FINISHED |
| Object | sl(2,R) |
—
|
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: sl(2,R) | Statement: [sl(2,C), realForm, sl(2,R)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realForm Context triple: [sl(2,C), realForm, sl(2,R)]
-
A.
realForm
chosen
Indicates that one entity is the actual, concrete or physical form or manifestation of another entity (such as an abstract, alternate, or disguised version).
-
B.
hasRealForm
Indicates that an abstract, conceptual, or non-physical entity is associated with a concrete, physical manifestation or embodiment.
-
C.
hasRealFormOf
Indicates that one entity is the concrete, real-world manifestation or physical form of another, more abstract or conceptual entity.
-
D.
isRealFormOf
Indicates that one entity is the actual, physically existing or fully realized version of another entity, which may be abstract, conceptual, or a representation.
-
E.
formalRealization
Indicates that an abstract work, plan, or design is concretely implemented or expressed in a specific formal product, version, or representation.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6257a5ae881908db3032511378836 |
completed | May 2, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:26 a.m.