Triple
T25094901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Planets |
E628560
|
entity |
| Predicate | excludesPlanet |
P158402
|
FINISHED |
| Object | Earth |
—
|
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: Earth | Statement: [The Planets, excludesPlanet, Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excludesPlanet Context triple: [The Planets, excludesPlanet, Earth]
-
A.
excludes
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
-
B.
excludedFrom
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
C.
excludesPrimary
Indicates that one entity explicitly omits or does not include another entity as its primary or main component, option, or classification.
-
D.
excludesPower
Indicates that one entity denies, removes, or prevents another entity from having or exercising a particular power or authority.
-
E.
excludedColony
Indicates that a colony is deliberately left out from inclusion, consideration, or participation in a specified set, group, or process.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46d3f35848190b56a4373c97a7d64 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 18, 2026, 6:24 a.m.