Triple
T29138934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covenant |
E738576
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Halo universe organization |
C35327
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Halo universe organization Context triple: [Covenant, instanceOf, Halo universe organization]
-
A.
organization in the Halo universe
chosen
An organization in the Halo universe is a structured group—such as a military, governmental, corporate, or religious faction—composed of individuals or species working together under a defined hierarchy and purpose to influence events within the Halo setting.
-
B.
Mass Effect organization
A Mass Effect organization is a structured group or faction within the Mass Effect universe that coordinates resources, personnel, and strategic objectives to influence galactic events, politics, or conflicts.
-
C.
in-universe organization
An in-universe organization is a fictional group, institution, or entity that operates within a story’s setting, shaping events, characters, and world dynamics according to its goals, structure, and culture.
-
D.
UNSC military personnel
UNSC military personnel are the organized, trained, and equipped members of the United Nations Space Command’s armed forces responsible for conducting space, air, land, and naval operations to defend humanity and its interests.
-
E.
Star Wars organization
A Star Wars organization is a structured group or faction within the Star Wars universe, defined by a common purpose, ideology, or function that influences galactic events and character relationships.
- F. None of above.
Provenance (1 batch)
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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:35 a.m.