Triple
T10229222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suliformes |
E243295
|
entity |
| Predicate | timeRecognizedAsSeparateOrder |
P56928
|
FINISHED |
| Object | late 20th 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: late 20th century | Statement: [Suliformes, timeRecognizedAsSeparateOrder, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeRecognizedAsSeparateOrder Context triple: [Suliformes, timeRecognizedAsSeparateOrder, late 20th century]
-
A.
accuracyOrderTime
Indicates the degree to which the recorded or predicted time of an order matches its actual or intended time.
-
B.
establishedForOrder
Indicates that something has been created or set up specifically to serve, support, or fulfill a particular order.
-
C.
timePeriodRecognized
chosen
Indicates that a specific span of time has been formally identified or acknowledged as significant or valid within a given context.
-
D.
recognizesOrders
Indicates that one entity formally acknowledges and accepts the orders or directives issued by another entity.
-
E.
establishedWithOrder
Indicates that something is created, initiated, or set up in accordance with a specified order or sequence.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:18 a.m.