Triple
T27811475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batuu |
E702528
|
entity |
| Predicate | activeGroup |
P130799
|
FINISHED |
| Object | Resistance |
—
|
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: Resistance | Statement: [Batuu, activeGroup, Resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeGroup Context triple: [Batuu, activeGroup, Resistance]
-
A.
allyGroup
chosen
Indicates that two or more entities belong to the same allied group or faction, cooperating or aligned in purpose or interests.
-
B.
controlGroup
Indicates that one entity functions as the control group against which another condition, treatment, or experimental group is compared.
-
C.
interactsWithGroup
Indicates that an entity engages in actions or exchanges with a collective group of other entities.
-
D.
usesGroup
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
-
E.
formedGroup
Indicates that multiple entities have come together to create or establish a group or collective unit.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 5:42 p.m.