Triple
T11958174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GAS |
E284603
|
entity |
| Predicate | supportsRelocation |
P46455
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [GAS, supportsRelocation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRelocation Context triple: [GAS, supportsRelocation, yes]
-
A.
requiredRelocationFrom
Indicates that one entity mandates or necessitates the relocation of another entity away from a specified source location or context.
-
B.
requiredRelocationTo
Indicates that one entity must move or be transferred to another specified location or entity as a necessary condition or requirement.
-
C.
relocatedWithSupportFrom
chosen
Indicates that an entity moved or was transferred to a new location with assistance, backing, or resources provided by another entity.
-
D.
hasRelocation
Indicates that one entity is moved, transferred, or reassigned from one location or context to another.
-
E.
continuedAfterRelocation
Indicates that the same relationship or activity persisted without interruption after one of the involved entities changed location or was relocated.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903681a00819098c2b5260e2ef834 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.