Triple
T12009854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night's Watch |
E285877
|
entity |
| Predicate | internalDivision |
P99142
|
FINISHED |
| Object | rangers |
—
|
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: rangers | Statement: [Night's Watch, internalDivision, rangers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalDivision Context triple: [Night's Watch, internalDivision, rangers]
-
A.
hadInternalDivision
Indicates that an entity experienced a split or conflict within its own members, factions, or components.
-
B.
companyInternal
Indicates that the relationship or action occurs within the same company or is restricted to internal company context.
-
C.
relatedDivision
Indicates that there is an organizational or structural association between two divisions, such as being counterparts, partners, or otherwise linked within a broader entity.
-
D.
dividedIn
chosen
Indicates that one entity is partitioned or separated into multiple distinct parts, sections, or groups represented by another entity.
-
E.
companyDivision
Indicates that one entity is a division, branch, or subordinate business unit within the organizational structure of another company entity.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d61a4c81909e6cb6500b61df94 |
completed | April 10, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.