Triple
T9395736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back to the Egg |
E226137
|
entity |
| Predicate | hasLooseConcept |
P88710
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Back to the Egg, hasLooseConcept, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLooseConcept Context triple: [Back to the Egg, hasLooseConcept, yes]
-
A.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
B.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
C.
hasImplementedConcept
Indicates that an entity has put a particular concept into practice or realized it in an implemented form.
-
D.
hasConceptualBoundary
Indicates that one entity defines, marks, or establishes the abstract limit or scope of another entity’s meaning, applicability, or conceptual extent.
-
E.
isConceptual
Indicates that something exists as an abstract or theoretical idea rather than as a concrete, physical entity.
- 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_69ca842f7e3481908bf5bcf52e032dbd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5112faa08190a8dd2c461d1e7a14 |
completed | April 1, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:45 p.m.