Triple
T15622612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cash Bundren |
E375593
|
entity |
| Predicate | hasInternalLogic |
P48245
|
FINISHED |
| Object | lists reasons for coffin design |
—
|
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: lists reasons for coffin design | Statement: [Cash Bundren, hasInternalLogic, lists reasons for coffin design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternalLogic Context triple: [Cash Bundren, hasInternalLogic, lists reasons for coffin design]
-
A.
hasInternalDisplay
Indicates that an entity is equipped with a built-in display screen as part of its own hardware.
-
B.
hasLogicalStructure
chosen
Indicates that one entity possesses or exhibits a specific underlying logical organization or pattern defined by another entity.
-
C.
hasInternalIssue
Indicates that an entity is experiencing a problem, fault, or malfunction originating within itself or its internal components or processes.
-
D.
hasInteriorBehavior
Indicates that an entity exhibits a particular behavior or set of behaviors within its internal or enclosed space.
-
E.
hasImplementationDetail
Indicates that one entity specifies or contains a concrete implementation detail or internal mechanism related to another entity.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e9cfd94819091459aa17a002eaf |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.