Triple
T26943402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nightsisters |
E678575
|
entity |
| Predicate | governanceOver |
P760
|
FINISHED |
| Object | Nightbrothers |
—
|
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: Nightbrothers | Statement: [Nightsisters, governanceOver, Nightbrothers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governanceOver Context triple: [Nightsisters, governanceOver, Nightbrothers]
-
A.
governance
Indicates the relationship in which one entity exercises authority, control, or decision-making power over the policies, actions, or direction of another entity or system.
-
B.
governanceIncludes
Indicates that a governance structure or framework encompasses, incorporates, or has authority over the specified component, process, or entity.
-
C.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
-
D.
governs
chosen
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
E.
governanceView
Indicates a perspective, framework, or representation of how governance is structured, managed, or overseen within a given context.
- 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_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 27, 2026, 6:20 a.m.