Triple
T6937554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Museum of Broken Relationships |
E160589
|
entity |
| Predicate | hasObjectTypes |
P74380
|
FINISHED |
| Object | letters |
—
|
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: letters | Statement: [Museum of Broken Relationships, hasObjectTypes, letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObjectTypes Context triple: [Museum of Broken Relationships, hasObjectTypes, letters]
-
A.
hasObject
Indicates that an entity is associated with or possesses a particular object as part of a relationship or action.
-
B.
hasNumberOfObjects
Indicates that an entity is associated with a specific count or quantity of objects.
-
C.
hasTypeSystem
Indicates that an entity employs, is governed by, or is associated with a particular type system (a defined set of rules for classifying and constraining types).
-
D.
hasCollectionType
Indicates that an entity is associated with or organized under a specific type or category of collection.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6e0c620f0819080e0ec49b36d4c30 |
completed | March 27, 2026, 7:55 p.m. |
Created at: March 27, 2026, 2:28 p.m.