Triple
T31925908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCTV Headquarters structural concept |
E815107
|
entity |
| Predicate | resistsAction |
P67874
|
FINISHED |
| Object | gravity loads |
—
|
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: gravity loads | Statement: [CCTV Headquarters structural concept, resistsAction, gravity loads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resistsAction Context triple: [CCTV Headquarters structural concept, resistsAction, gravity loads]
-
A.
resistedIn
Indicates that an entity actively opposed, withstood, or fought against something within a specific context, event, or location.
-
B.
resistedUntil
Indicates that an entity continued to oppose or withstand another entity or force up to a specific point in time or event.
-
C.
refusedToAbdicate
Indicates that a person who holds power or authority declined to give up or renounce their position when expected or requested to do so.
-
D.
resistedUnderLeader
Indicates that an entity engaged in resistance or opposition while being directed or led by a specified leader.
-
E.
isResistant
chosen
Indicates that an entity can withstand, oppose, or is not significantly affected by a specified force, influence, or agent.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:03 a.m.