Triple
T35730244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Chase |
E1032730
|
entity |
| Predicate | governingBodyRequirement |
P128347
|
FINISHED |
| Object | FIA |
E158007
|
NE 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: FIA | Statement: [The Chase, governingBodyRequirement, FIA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyRequirement Context triple: [The Chase, governingBodyRequirement, FIA]
-
A.
governingBodyIncludes
Indicates that a governing body has a particular entity as one of its members or constituent parts.
-
B.
governingBodyRepresents
Indicates that a governing body acts on behalf of, and makes decisions representing the interests or authority of, another entity.
-
C.
governingBodyOrSupport
Indicates that one entity serves as the governing authority for, or provides official support to, another entity.
-
D.
mandatingBody
chosen
Indicates that one entity serves as the authoritative body that issues or imposes a mandate, requirement, or directive on another entity or activity.
-
E.
governingBody2
Indicates that an entity serves as the official authority or administrative body responsible for overseeing, managing, or regulating another entity.
- F. None of above.
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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01e993fec0819090cc397218515e88 |
completed | May 11, 2026, 2:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387d1d14f881908531994f5ebc50c6 |
completed | June 22, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_6a01e57594188190a2354f48cf71b48c |
completed | May 11, 2026, 2:19 p.m. |
Created at: May 3, 2026, 4:05 p.m.