Triple
T7462438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Companion Pass |
E176283
|
entity |
| Predicate | canChangeCompanion |
P5524
|
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: [Companion Pass, canChangeCompanion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canChangeCompanion Context triple: [Companion Pass, canChangeCompanion, true]
-
A.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
B.
canBeModifiedBetween
Indicates that something is allowed or able to be changed during a specified interval or between defined points or states.
-
C.
switchesPlacesWith
Indicates that two entities exchange their respective positions or roles with each other.
-
D.
canSet
chosen
Indicates that one entity has the ability or permission to assign, configure, or change a property, value, or state of another entity.
-
E.
canBeConvenedBy
Indicates that an entity (such as a group, body, or meeting) may be formally brought together or assembled by a specified agent or authority.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d80ae08190ba383066cf0cb2ce |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:39 p.m.