Triple
T3389225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Vortex |
E71376
|
entity |
| Predicate | canBeManipulatedBy |
P12017
|
FINISHED |
| Object | advanced Time Lord technology |
—
|
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: advanced Time Lord technology | Statement: [Time Vortex, canBeManipulatedBy, advanced Time Lord technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeManipulatedBy Context triple: [Time Vortex, canBeManipulatedBy, advanced Time Lord technology]
-
A.
canControl
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
B.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
C.
mayBeModifiedBy
chosen
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
D.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
E.
canOwn
Indicates that one entity is permitted or legally able to possess or hold ownership rights over another entity.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb666e514819090560d43bfaf55b8 |
completed | March 8, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69ada43615f08190ac2275020d157983 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.