Triple
T25638030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adrastea |
E642758
|
entity |
| Predicate | belongsToCountryOfDiscovery |
P16041
|
FINISHED |
| Object | United States |
—
|
NE NERFINISHED |
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: United States | Statement: [Adrastea, belongsToCountryOfDiscovery, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCountryOfDiscovery Context triple: [Adrastea, belongsToCountryOfDiscovery, United States]
-
A.
eraOfDiscovery
Indicates a relationship where something belongs to, occurs in, or is characteristic of a specific era of discovery or exploration.
-
B.
countryOfExploration
Indicates the country under whose auspices or within whose territory an exploration activity was conducted.
-
C.
isDiscoveredBy
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
-
D.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
E.
discoveredInCountry
chosen
Indicates that something was discovered within the geographical boundaries or jurisdiction of a specified country.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 21, 2026, 5:36 p.m.