Triple
T20392610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humans (Star Trek) |
E498120
|
entity |
| Predicate | roleInFederation |
P6756
|
FINISHED |
| Object | founding member |
—
|
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: founding member | Statement: [Humans (Star Trek), roleInFederation, founding member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFederation Context triple: [Humans (Star Trek), roleInFederation, founding member]
-
A.
roleInStellarFusion
Indicates the specific function or contribution an entity has within the processes that drive stellar nuclear fusion.
-
B.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
C.
roleInIntegration
Indicates the specific function or responsibility an entity has within a combined or coordinated system, process, or integration.
-
D.
allianceRole
chosen
Indicates the specific function, status, or responsibility an entity holds within an alliance or cooperative partnership.
-
E.
roleInCluster
Indicates the specific function or position an entity holds within a defined group or cluster of related entities.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e679108b1481909677cf80e8e77e76 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.