Triple
T7632121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casa Colorada |
E172781
|
entity |
| Predicate | hasFunctionHypothesis |
P14769
|
FINISHED |
| Object | residential building |
—
|
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: residential building | Statement: [Casa Colorada, hasFunctionHypothesis, residential building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionHypothesis Context triple: [Casa Colorada, hasFunctionHypothesis, residential building]
-
A.
functionHypothesis
chosen
Indicates that an entity is proposed or assumed to serve as a function or functional explanation for another entity or phenomenon.
-
B.
proposesHypothesis
Indicates that one entity puts forward a tentative explanation or hypothesis for consideration regarding another entity or phenomenon.
-
C.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
D.
hasTheory
Indicates that an entity possesses, is associated with, or is characterized by a particular theory.
-
E.
primaryFunctionHypothesis
Indicates a hypothesized main role or purpose that one entity is proposed to serve in relation to another or within a given 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faa4d2808190942129110711788b |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:57 p.m.