Triple
T220358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Rights Day |
E4198
|
entity |
| Predicate | firstObservedAfter |
P4411
|
FINISHED |
| Object | adoption of the Universal Declaration of Human Rights |
—
|
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: adoption of the Universal Declaration of Human Rights | Statement: [Human Rights Day, firstObservedAfter, adoption of the Universal Declaration of Human Rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstObservedAfter Context triple: [Human Rights Day, firstObservedAfter, adoption of the Universal Declaration of Human Rights]
-
A.
observedAt
Indicates that an entity was recorded or noticed at a specific time or place.
-
B.
introducedAfter
chosen
Indicates that one entity was introduced at a later time or stage than another entity.
-
C.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
D.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
E.
firstRaisedAt
Indicates the initial time or context at which an issue, topic, or matter was first brought up or introduced.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25efd0df48190b8fef4c422a1265f |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b54d790819093b35bd1a6f00f92 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.