Triple
T29852552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asgard archaea |
E758100
|
entity |
| Predicate | wereFirstReportedIn |
P14790
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Asgard archaea, wereFirstReportedIn, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereFirstReportedIn Context triple: [Asgard archaea, wereFirstReportedIn, 2015]
-
A.
wasFirstObservedIn
Indicates that an entity was initially noticed, recorded, or detected at a particular time or place.
-
B.
firstReportedYear
chosen
Indicates the year in which something was initially reported, documented, or made known for the first time.
-
C.
firstClearlyRecognizedIn
Indicates the point in time or context when something was first clearly identified, acknowledged, or distinguished as such.
-
D.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
E.
firstWidelyObserved
Indicates that something was initially noticed or recorded by a large number of observers or across a broad context for the first time.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67648f35c8190ab466e413b6dbcb5 |
completed | May 2, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:44 p.m.