Triple
T30863380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth orbit |
E786123
|
entity |
| Predicate | hasReferencePoint |
P91203
|
FINISHED |
| Object | perigee |
—
|
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: perigee | Statement: [Earth orbit, hasReferencePoint, perigee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReferencePoint Context triple: [Earth orbit, hasReferencePoint, perigee]
-
A.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
B.
hasReferenceID
Indicates that an entity is associated with a specific reference identifier used to uniquely track or distinguish it.
-
C.
hasDistanceReference
Indicates that a distance value is specified relative to a particular reference point, scale, or standard.
-
D.
hasConfluencePointAt
Indicates that two or more flows, paths, or entities meet and merge at a specific point.
-
E.
usesBasePoint
chosen
Indicates that one entity performs an operation or defines a structure by referencing or relying on a specific base point.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00b6e163308190adeb1d6eb8558641 |
completed | May 10, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_6a00b67e0e388190b08ad66cee4cb0d7 |
completed | May 10, 2026, 4:46 p.m. |
Created at: April 29, 2026, 8:47 p.m.