Triple
T27131535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCD |
E681573
|
entity |
| Predicate | isInstitutionallyHeld |
P162056
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [MCD, isInstitutionallyHeld, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInstitutionallyHeld Context triple: [MCD, isInstitutionallyHeld, true]
-
A.
holdingInstitution
Indicates that one entity serves as the institution that holds, houses, or maintains custody of another entity (such as an item, collection, or resource).
-
B.
isInstitutional
Indicates that an entity functions as or is classified as an institution within the given context.
-
C.
hasInstitutionalControl
Indicates that one entity exercises formal authority, governance, or decision-making power over an institution or organizational body.
-
D.
hasInstitutionalCharacter
Indicates that something possesses qualities, status, or attributes associated with a formal institution or institutional framework.
-
E.
hasInstitutionalPresenceIn
Indicates that an institution maintains an established presence, such as operations, offices, or activities, within a specified location or region.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6247832a48190b820e8c0c22ff5db |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621c7d3e0819095b1f327637ae4f9 |
completed | May 2, 2026, 4:09 p.m. |
Created at: April 27, 2026, 9:04 a.m.