Triple
T14286967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Valiant |
E354199
|
entity |
| Predicate | isMobileBase |
P113627
|
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: [The Valiant, isMobileBase, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMobileBase Context triple: [The Valiant, isMobileBase, true]
-
A.
mobileVariant
Indicates that one entity is a mobile-specific version or adaptation of another entity.
-
B.
isFeatureBased
Indicates that one entity is derived from, determined by, or constructed using the characteristics or attributes of another entity.
-
C.
supportsLTE
Indicates that one entity provides compatibility with or functionality for LTE (Long-Term Evolution) cellular communication for another entity.
-
D.
hasCellularModel
Indicates that one entity serves as a cellular (cell-based) model or system used to study, represent, or simulate the biological properties or behavior of another entity.
-
E.
hasBaseSystem
Indicates that one entity is founded upon, derived from, or primarily operates using another entity as its underlying system or framework.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697ef40c8190bea37724b28c2e99 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:11 a.m.