Triple
T8229199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freedom or Death |
E192246
|
entity |
| Predicate | hasBinaryStructure |
P48977
|
FINISHED |
| Object | freedom versus death |
—
|
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: freedom versus death | Statement: [Freedom or Death, hasBinaryStructure, freedom versus death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBinaryStructure Context triple: [Freedom or Death, hasBinaryStructure, freedom versus death]
-
A.
hasBinary
Indicates that one entity is associated with another entity in a binary (two-component) relationship, typically as one of the two members of a pair.
-
B.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
C.
hasSignificantStructure
Indicates that an entity possesses a structure or internal organization that is notably complex, important, or meaningful in a given context.
-
D.
hasTwoPartStructure
chosen
Indicates that something is composed of exactly two distinct, structured parts that together form a whole.
-
E.
hasStructureCount
Indicates the number of structures associated with or contained by a given 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7802417c81908837c31136c41a5c |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.