Triple
T1065028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mardi Gras celebrations |
E22989
|
entity |
| Predicate | involvesOrganizationType |
P3580
|
FINISHED |
| Object | krewes |
—
|
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: krewes | Statement: [Mardi Gras celebrations, involvesOrganizationType, krewes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesOrganizationType Context triple: [Mardi Gras celebrations, involvesOrganizationType, krewes]
-
A.
responsibleOrganizationType
Indicates the type or category of organization that holds responsibility for a given action, resource, or obligation.
-
B.
organizationType
chosen
Indicates the specific category or classification of an organization in terms of its nature, structure, or primary function.
-
C.
hasTypeOfOrganization
Indicates that an entity is classified as belonging to a particular type or category of organization.
-
D.
controlledOrganization
Indicates that one entity has the authority to direct, manage, or significantly influence the operations and decisions of another organization.
-
E.
parentOrganizationType
Indicates the classification or category of the organization that serves as the parent in a hierarchical relationship.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b90f91248190ace1534a51b82bdd |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b7359eb881909c868a558861cc18 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.