Triple
T7265340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toon Army |
E159757
|
entity |
| Predicate | associatedIdentity |
P59181
|
FINISHED |
| Object | Geordie culture |
—
|
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: Geordie culture | Statement: [Toon Army, associatedIdentity, Geordie culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedIdentity Context triple: [Toon Army, associatedIdentity, Geordie culture]
-
A.
affiliateOfType
Indicates that an affiliate entity belongs to, or is categorized under, a specific type or classification.
-
B.
localIdentity
chosen
Indicates that an entity’s identity or role is defined specifically within a particular local context, scope, or environment, rather than globally.
-
C.
subjectIdentity
Indicates that two or more references correspond to the same underlying entity or individual identity.
-
D.
realmAssociatedWith
Indicates an association or connection between an entity and a particular realm, domain, or sphere with which it is linked or to which it pertains.
-
E.
originallyAssociatedWith
Indicates that an entity was first linked, connected, or affiliated with another entity before any later changes in association.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:57 p.m.