Triple
T26004737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Brutus |
E646726
|
entity |
| Predicate | movementCapability |
P159654
|
FINISHED |
| Object | no longer self-propelled |
—
|
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: no longer self-propelled | Statement: [Big Brutus, movementCapability, no longer self-propelled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementCapability Context triple: [Big Brutus, movementCapability, no longer self-propelled]
-
A.
movementFunction
Indicates a functional or operational role related to enabling, controlling, or characterizing movement between entities.
-
B.
movementCharacteristic
Indicates how an entity moves or behaves in motion, such as its style, pattern, or quality of movement.
-
C.
movementDomain
Indicates the general area, medium, or context within which a movement or motion takes place.
-
D.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
E.
movementSupported
Indicates that an entity’s movement is enabled, facilitated, or allowed by another entity or system.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6057964948190b3ecab50a47a5e7c |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 9 a.m.