Triple
T32069788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of England (Cars) |
E818976
|
entity |
| Predicate | universeRule |
P173511
|
FINISHED |
| Object | vehicles are sentient |
—
|
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: vehicles are sentient | Statement: [Queen of England (Cars), universeRule, vehicles are sentient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: universeRule Context triple: [Queen of England (Cars), universeRule, vehicles are sentient]
-
A.
typicalUniverse
Indicates that something represents or belongs to a standard, representative, or commonly occurring universe within a given context or model.
-
B.
universe
Indicates that something pertains to, exists within, or is associated with the entirety of space, time, matter, and phenomena collectively referred to as the universe.
-
C.
settingInUniverse
Indicates that one entity is set or takes place within the fictional universe defined by another entity.
-
D.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
E.
universeNumber
Indicates that an entity is associated with a specific universe identified by a particular number or index.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:23 a.m.