Triple
T25745570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | inner Solar System |
E648335
|
entity |
| Predicate | containsHumanSpaceActivityRegion |
P178256
|
FINISHED |
| Object | Earth orbit |
—
|
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: Earth orbit | Statement: [inner Solar System, containsHumanSpaceActivityRegion, Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsHumanSpaceActivityRegion Context triple: [inner Solar System, containsHumanSpaceActivityRegion, Earth orbit]
-
A.
hasActivityRegion
Indicates the geographic or spatial region within which an activity occurs or is applicable.
-
B.
hasAuthorActivityRegion
Indicates the geographical region in which an author is or was primarily active in their professional or creative work.
-
C.
hasSpacetimeRegion
Indicates that something occupies, is associated with, or is bounded by a specific region in spacetime.
-
D.
hasHumanActivities
Indicates that certain human actions, behaviors, or practices are present, performed, or associated with a given entity.
-
E.
hasProtectedAreaActivity
Indicates that an entity engages in or is associated with a specific activity occurring within a protected area.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 22, 2026, 3:51 a.m.