Triple
T31207644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ether |
E795644
|
entity |
| Predicate | recordLaterDiscoveredBy |
P191591
|
FINISHED |
| Object | Limhi’s people |
—
|
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: Limhi’s people | Statement: [Ether, recordLaterDiscoveredBy, Limhi’s people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordLaterDiscoveredBy Context triple: [Ether, recordLaterDiscoveredBy, Limhi’s people]
-
A.
laterDiscovered
Indicates that one entity was discovered or found at a time subsequent to the discovery of another entity.
-
B.
remainsDiscoveredBy
Indicates that physical remains (such as fossils, artifacts, or bodies) were found or uncovered by a particular discoverer or discovering entity.
-
C.
isDiscoveredBy
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
-
D.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
E.
recordLaterAbridgedBy
Indicates that a complete recording is later released in a shortened or condensed form by another recording.
- F. None of above. chosen
Provenance (4 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:09 p.m.