Triple
T37456789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spine Crawler |
E930819
|
entity |
| Predicate | requiresCreep |
P202060
|
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: [Spine Crawler, requiresCreep, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresCreep Context triple: [Spine Crawler, requiresCreep, true]
-
A.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
B.
hasEnergyRequirement
Indicates that one entity requires a specified amount or type of energy in order for a process, function, or state to occur or be maintained.
-
C.
requiresForDefense
Indicates that one entity must have or obtain another entity as a necessary condition to provide or maintain defense.
-
D.
requiresCall
Indicates that one entity must initiate or receive a phone call or similar direct voice communication with another entity as a necessary condition for some action or state.
-
E.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a004a8892c08190bcacb952ad737716 |
completed | May 10, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_6a004a44b4948190be4b3dbfce8da020 |
completed | May 10, 2026, 9:05 a.m. |
| PDg | Predicate description generation | batch_6a004a87bb908190a2bd164a60245f1d |
completed | May 10, 2026, 9:06 a.m. |
Created at: May 3, 2026, 4:17 p.m.