Triple
T630910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney's All-Star Music Resort |
E15923
|
entity |
| Predicate | isFamilyFriendly |
P17278
|
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: [Disney's All-Star Music Resort, isFamilyFriendly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFamilyFriendly Context triple: [Disney's All-Star Music Resort, isFamilyFriendly, true]
-
A.
familyControlled
Indicates that an entity is owned or effectively governed by one or more members of the same family, who hold decisive control over its decisions or operations.
-
B.
usedByFamily
Indicates that something is regularly utilized or consumed by a family as a group.
-
C.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
D.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
E.
TVShare
Indicates a relationship where one entity shares access to or usage of a television (or TV-related content/service) with another entity.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec171008190ab91dee86e9279af |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49defe58c8190bd39ef47c9f660a7 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.