Triple
T7680672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lycaon |
E173983
|
entity |
| Predicate | runningAdaptationOfSpecies |
P78900
|
FINISHED |
| Object | longDistancePursuit |
—
|
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: longDistancePursuit | Statement: [Lycaon, runningAdaptationOfSpecies, longDistancePursuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runningAdaptationOfSpecies Context triple: [Lycaon, runningAdaptationOfSpecies, longDistancePursuit]
-
A.
runBySpecies
Indicates that an activity, process, or organization is operated or conducted by a particular species.
-
B.
adaptationSuccess
Indicates that an entity has effectively adjusted or responded to a change in conditions, environment, or requirements.
-
C.
adaptationIn
Indicates that something appears, is represented, or takes place within a particular adaptation of an original work.
-
D.
adaptationType
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
E.
adaptation
Indicates a relationship where one entity changes or is modified to better suit, function within, or correspond to another entity or context.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69c7048a01508190bc2e9ae8b863486c |
completed | March 27, 2026, 10:28 p.m. |
Created at: March 27, 2026, 4:01 p.m.