Triple
T8124272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gunners |
E189683
|
entity |
| Predicate | associatedBranchType |
P1988
|
FINISHED |
| Object | artillery corps |
—
|
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: artillery corps | Statement: [The Gunners, associatedBranchType, artillery corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedBranchType Context triple: [The Gunners, associatedBranchType, artillery corps]
-
A.
relatesToBranch
Indicates a general association or connection between an entity and a specific branch (such as a subdivision, offshoot, or subunit) within a larger structure or system.
-
B.
affectedBranch
Indicates that one entity is a branch that is impacted or influenced by the state or actions associated with another entity.
-
C.
representedBranch
Indicates that one entity serves as a representative or proxy for a particular branch of another entity or organization.
-
D.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
E.
branchType
chosen
Indicates the specific kind or category of branch that an entity belongs to or is associated with.
- 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_69ca82bb74848190afb1f18640632c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4c2e388190b86854f8b1765e61 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb3696379c8190a20965e59ed8f370 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:34 p.m.