Triple
T24576206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition League |
E608115
|
entity |
| Predicate | teamLocationType |
P156399
|
FINISHED |
| Object | smaller communities |
—
|
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: smaller communities | Statement: [Expedition League, teamLocationType, smaller communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamLocationType Context triple: [Expedition League, teamLocationType, smaller communities]
-
A.
teamLocation
Indicates that a team is based in, associated with, or operates from a particular geographic location.
-
B.
teamLocationExample
Indicates that a specific location is provided as an example of where a team is based or operates.
-
C.
teamLocationScope
Indicates the geographic or organizational area within which a team operates or is considered relevant.
-
D.
teamLocationCriterion
Indicates a condition that specifies or restricts where a team must be located.
-
E.
associatedWithTeamLocation
Indicates that an entity has a relationship or connection to the geographic location of a specific team.
- F. None of above. chosen
Provenance (4 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9295ab08190b6c137c99bcd958f |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:29 a.m.