Triple
T33997851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L9 Nord |
E871724
|
entity |
| Predicate | hasBranchRelation |
P33476
|
FINISHED |
| Object | L9 Sud |
—
|
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: L9 Sud | Statement: [L9 Nord, hasBranchRelation, L9 Sud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchRelation Context triple: [L9 Nord, hasBranchRelation, L9 Sud]
-
A.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
B.
hasBranchRole
Indicates that an entity holds or is assigned a specific role or position within a particular branch or subdivision of an organization.
-
C.
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.
-
D.
hasBranchName
Indicates that an entity (such as a branch or subdivision) bears or is identified by a specific branch name.
-
E.
hasRelation
chosen
Indicates that there exists some specified relationship or association between two entities.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 1:50 a.m.