Triple
T23532667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Five game |
E576611
|
entity |
| Predicate | isNotDefinedBy |
P23080
|
FINISHED |
| Object | ecological importance alone |
—
|
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: ecological importance alone | Statement: [Big Five game, isNotDefinedBy, ecological importance alone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotDefinedBy Context triple: [Big Five game, isNotDefinedBy, ecological importance alone]
-
A.
doesNotDefine
chosen
Indicates that one entity does not provide a definition, specification, or determining description for another entity.
-
B.
notDefinedPrimarilyBy
Indicates that one entity is not chiefly or fundamentally characterized, identified, or determined by another entity or attribute.
-
C.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
D.
endDefinedBy
Indicates that the termination or boundary of one entity is determined, specified, or constrained by another entity.
-
E.
isNotIndicatedFor
Indicates that a treatment, action, or option is not recommended or appropriate for a particular condition, situation, or 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac79800081908907bce55b9c68cf |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.