Triple
T28374813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Animation Academy |
E718727
|
entity |
| Predicate | allowsGuestsTo |
P273
|
FINISHED |
| Object | take home their drawings |
—
|
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: take home their drawings | Statement: [Animation Academy, allowsGuestsTo, take home their drawings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsGuestsTo Context triple: [Animation Academy, allowsGuestsTo, take home their drawings]
-
A.
supportsGuest
Indicates that one entity provides assistance, resources, or accommodation to another entity in the role of a guest.
-
B.
allowsIndividualAccess
Indicates that one entity grants another entity permission to access something on an individual, per-person basis.
-
C.
allowsReservationsOn
Indicates that one entity permits making reservations or bookings for another entity.
-
D.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
E.
allowsReservation
Indicates that one entity permits another entity to make or hold a reservation for its use or access.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 1:02 a.m.