Triple
T26942790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kree Empire |
E678563
|
entity |
| Predicate | subjugatedClass |
P137200
|
FINISHED |
| Object | pink Kree |
—
|
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: pink Kree | Statement: [Kree Empire, subjugatedClass, pink Kree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjugatedClass Context triple: [Kree Empire, subjugatedClass, pink Kree]
-
A.
indicatesSubjugation
chosen
Indicates that one entity is under the domination, control, or authority of another, reflecting a hierarchical power imbalance or enforced obedience.
-
B.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
-
C.
subordinateTo
Indicates that one entity holds a lower rank, status, or authority and is subject to the control, direction, or oversight of another entity.
-
D.
subsumedBy
Indicates that one entity is more specific and fully contained within another, more general entity in a hierarchical or set-inclusion sense.
-
E.
tiltingSubClass
Indicates that one class is a specialized tilting-related subclass or refinement of another class within a hierarchical relationship.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620822d6081908e38814f5a1c0931 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:19 a.m.