Triple
T32138883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hylaeosaurus |
E820848
|
entity |
| Predicate | fossilDiscoveryCentury |
P5649
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Hylaeosaurus, fossilDiscoveryCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilDiscoveryCentury Context triple: [Hylaeosaurus, fossilDiscoveryCentury, 19th century]
-
A.
discoveredInCentury
chosen
Indicates that an entity was discovered during a specific century.
-
B.
majorFossilDiscoveriesBegan
Indicates that the time or event specified marks the beginning of significant fossil discovery activities or findings.
-
C.
revealedInCentury
Indicates that something became known, disclosed, or publicly revealed during a specified century.
-
D.
fossilDiscoverer
Indicates the relationship in which an agent is the one who discovered or unearthed a particular fossil.
-
E.
excavatedSinceCentury
Indicates that an entity has been excavated starting from, or at some point during or after, a specified century.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9ab515c819086bb604281251227 |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:30 a.m.