Triple
T10784073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | golden bowl (symbol in The Golden Bowl) |
E254405
|
entity |
| Predicate | defect |
P95465
|
FINISHED |
| Object | hidden crack |
—
|
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: hidden crack | Statement: [golden bowl (symbol in The Golden Bowl), defect, hidden crack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defect Context triple: [golden bowl (symbol in The Golden Bowl), defect, hidden crack]
-
A.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
-
B.
defectsFrom
Indicates a relationship where an entity abandons, deserts, or switches allegiance away from another entity, often to join an opposing side.
-
C.
defunct
Indicates that an entity has ceased to exist, operate, or function and is no longer active or in use.
-
D.
disadvantage
Indicates that one entity is in a less favorable, weaker, or hindered position relative to another in a given context.
-
E.
issue
Indicates that an entity formally publishes, releases, or distributes something, such as a document, statement, or item, often in an official or authoritative capacity.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d1b4bc8190871dd21265065705 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:17 p.m.