Triple
T12036679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metteniusales |
E286557
|
entity |
| Predicate | firstFormalRecognition |
P23896
|
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: [Metteniusales, firstFormalRecognition, 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFormalRecognition Context triple: [Metteniusales, firstFormalRecognition, 21st century]
-
A.
firstMajorRecognition
Indicates the earliest significant award, honor, or formal recognition received by an entity.
-
B.
recognitionDate
chosen
Indicates the date on which an entity, status, or achievement is formally acknowledged or officially recognized.
-
C.
wasRecognizedAs
Indicates that an entity was formally identified, acknowledged, or designated as having a particular role, status, or quality.
-
D.
formalizedAt
Indicates the point in time or event at which something is officially established, documented, or given formal status.
-
E.
firstSolutionRecognizedYear
Indicates the year in which the first known or accepted solution to a given problem or question was formally recognized.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.