Triple
T29105428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokitae |
E736748
|
entity |
| Predicate | tankSizeCriticism |
P166336
|
FINISHED |
| Object | considered undersized by activists |
—
|
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: considered undersized by activists | Statement: [Tokitae, tankSizeCriticism, considered undersized by activists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tankSizeCriticism Context triple: [Tokitae, tankSizeCriticism, considered undersized by activists]
-
A.
mainTankCapacity
Indicates the maximum volume of fuel or liquid that the primary tank is designed to hold.
-
B.
tankDesign
Indicates a relationship where an entity is responsible for or associated with the design or engineering of a tank.
-
C.
mainTankName
Indicates that the subject entity has the specified name as its primary or main tank designation.
-
D.
hasCentralTank
Indicates that an entity possesses or is equipped with a primary central tank as a key component or feature.
-
E.
hasTank
Indicates that an entity possesses, is equipped with, or contains a tank (such as a storage tank, fuel tank, or similar vessel).
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661b93fe48190b846fb7654dc7b7d |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 11:15 a.m.