Triple
T35722309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascensión |
E1032507
|
entity |
| Predicate | activeAsOf |
P190522
|
FINISHED |
| Object | 21st century |
—
|
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: 21st century | Statement: [Ascensión, activeAsOf, 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeAsOf Context triple: [Ascensión, activeAsOf, 21st century]
-
A.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
-
B.
activeAs
Indicates that an entity is currently functioning or serving in a particular role, capacity, or status.
-
C.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
D.
activatedAs
Indicates that one entity has been put into an active or operational state in the role or capacity of another specified entity.
-
E.
activeAfter
Indicates that one entity becomes active only after another specified event, state, or time has occurred.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: May 3, 2026, 4:05 p.m.