Triple
T24357384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AAFC |
E613959
|
entity |
| Predicate | teamDistribution |
P155908
|
FINISHED |
| Object | franchises in multiple U.S. cities |
—
|
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: franchises in multiple U.S. cities | Statement: [AAFC, teamDistribution, franchises in multiple U.S. cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamDistribution Context triple: [AAFC, teamDistribution, franchises in multiple U.S. cities]
-
A.
teamNumberRole
Indicates that a specific team, identified by its number, is associated with a particular role or function.
-
B.
teamDynamic
Indicates how members of a group interact, collaborate, and influence each other’s behavior and performance as a collective unit.
-
C.
teamBasedOn
Indicates that one entity (typically a team) is formed, organized, or defined on the basis of another entity (such as a criterion, source, or underlying structure).
-
D.
fieldsTeam
Indicates that an entity is a member of, or associated as part of, a particular team.
-
E.
teamDivision
Indicates how a larger team is split into smaller subgroups or units for organization or collaboration.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29349ee188190a9d54b2c725b8a27 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2 a.m.