Triple
T3377359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Citadel of the Time Lords |
E71095
|
entity |
| Predicate | hasDefense |
P1135
|
FINISHED |
| Object | temporal barriers |
—
|
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: temporal barriers | Statement: [Citadel of the Time Lords, hasDefense, temporal barriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefense Context triple: [Citadel of the Time Lords, hasDefense, temporal barriers]
-
A.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
-
B.
hasDefenderStrength
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
-
C.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
D.
typeOfDefense
chosen
Indicates the specific kind or category of defense employed or possessed in a given context.
-
E.
defenceHandledBy
Indicates that responsibility for managing or conducting a defence is assigned to or carried out by a particular agent or 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e8d1988190b6fb6c4c5502f25f |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.