Triple
T29474013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Life to Live |
E747591
|
entity |
| Predicate | hasNonlinearStructure |
P200961
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [My Life to Live, hasNonlinearStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNonlinearStructure Context triple: [My Life to Live, hasNonlinearStructure, true]
-
A.
isNonlinear
Indicates that the relationship or behavior between variables is not proportional or additive, so it cannot be accurately described by a straight-line (linear) function.
-
B.
hasStructuralCharacter
Indicates that one entity possesses a particular structural property, form, or configuration that characterizes it.
-
C.
hasSignificantStructure
Indicates that an entity possesses a structure or internal organization that is notably complex, important, or meaningful in a given context.
-
D.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
E.
hasNetworkStructure
Indicates that one entity possesses, exhibits, or is organized according to a particular network-based structure defined by another entity or specification.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
| PDg | Predicate description generation | batch_69ffbe9c7c348190b6b72455d6a3e3d8 |
completed | May 9, 2026, 11:09 p.m. |
Created at: April 28, 2026, 3:59 p.m.