Triple
T31280029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evolver |
E797636
|
entity |
| Predicate | robotBehavior |
P95244
|
FINISHED |
| Object | learns from each game level and becomes more dangerous |
—
|
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: learns from each game level and becomes more dangerous | Statement: [Evolver, robotBehavior, learns from each game level and becomes more dangerous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: robotBehavior Context triple: [Evolver, robotBehavior, learns from each game level and becomes more dangerous]
-
A.
robotFunction
Indicates the specific role, task, or operational purpose that a robot is designed or configured to perform.
-
B.
robotType
Indicates the specific category or kind of robot that an entity belongs to.
-
C.
robotFeature
chosen
Indicates that a robot possesses or is characterized by a particular feature or attribute.
-
D.
robotControlSystem
Indicates a relationship where a system monitors, directs, and coordinates the actions and behaviors of one or more robots.
-
E.
roverFunction
Indicates that an entity serves as a rover and specifies the function, role, or operational purpose it performs.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:13 p.m.