Triple
T18965387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skull Tower |
E464020
|
entity |
| Predicate | enclosedSince |
P133970
|
FINISHED |
| Object | 1892 |
—
|
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: 1892 | Statement: [Skull Tower, enclosedSince, 1892]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enclosedSince Context triple: [Skull Tower, enclosedSince, 1892]
-
A.
existsSince
Indicates that an entity has been in existence or valid from a specified point in time onward.
-
B.
concludedSince
Indicates that a particular event, process, or relationship has ended or been brought to a conclusion at some point after a specified reference time.
-
C.
representedSince
Indicates that one entity has been acting as a representative or agent for another entity continuously from a specified starting time.
-
D.
coveredSince
Indicates that one entity has been under the protection, applicability, or effect of another entity continuously starting from a specified point in time.
-
E.
controlledSince
Indicates that one entity has held control or authority over another entity starting from a specified point in time.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d663948190b496fbd2e69c7f43 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, noon