Triple
T548674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Yellow House |
E12787
|
entity |
| Predicate | catalog code (common name) |
P8090
|
FINISHED |
| Object | F464 |
—
|
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: F464 | Statement: [The Yellow House, catalog code (common name), F464]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalog code (common name) Context triple: [The Yellow House, catalog code (common name), F464]
-
A.
catalogCode
chosen
Indicates that an entity is assigned a specific catalog identifier or code used for classification or reference.
-
B.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
C.
hasCodeName
Indicates that an entity is known or referred to by a particular alternative name or alias, often used for secrecy or distinction.
-
D.
isOfficialCodeFor
Indicates that one entity serves as the formally recognized or authorized code that designates or identifies another entity.
-
E.
hasINSEECODE
Indicates that an entity is associated with a specific INSEE code, identifying it within the French national statistical and administrative system.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49900895c819092a131c185a758bf |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b957988190bc269e372df2f0b2 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.