Triple
T29371638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMPS |
E744869
|
entity |
| Predicate | usesHandoff |
P167961
|
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: [AMPS, usesHandoff, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHandoff Context triple: [AMPS, usesHandoff, yes]
-
A.
handoffType
Indicates the manner or category of how control, responsibility, or an item is transferred from one entity to another.
-
B.
supportsHandoverWith
Indicates that one entity is capable of transferring control, responsibility, or an ongoing process to another entity in a coordinated handover.
-
C.
reverseHandOffTo
Indicates transferring control, responsibility, or ownership of something back to the previous holder or source after it was handed off.
-
D.
handedOverOfficeDuring
Indicates that one entity transferred official control, authority, or responsibility of an office or position to another entity during a specified time period.
-
E.
handsOverTo
Indicates that one entity transfers possession, control, or responsibility of something directly to another entity.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66e5f7e30819094530abceabd5f43 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 2:27 p.m.