Triple
T32185724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Force Reserve |
E822102
|
entity |
| Predicate | sharesCoreValuesWith |
P114922
|
FINISHED |
| Object | United States Space Force |
—
|
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 Space Force | Statement: [Space Force Reserve, sharesCoreValuesWith, United States Space Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCoreValuesWith Context triple: [Space Force Reserve, sharesCoreValuesWith, United States Space Force]
-
A.
sharesValuesWith
chosen
Indicates that two entities hold similar or compatible beliefs, principles, or priorities.
-
B.
sharesComponentsWith
Indicates that two entities have one or more structural or functional components in common.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
sharesCommunityWith
Indicates that two entities belong to or participate in the same community or communal group.
-
E.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
Created at: May 1, 2026, 12:35 a.m.