Triple
T5322044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E.T. Adventure (Universal Studios Hollywood) |
E121695
|
entity |
| Predicate | rideDurationApprox |
P11363
|
FINISHED |
| Object | 4 minutes |
—
|
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: 4 minutes | Statement: [E.T. Adventure (Universal Studios Hollywood), rideDurationApprox, 4 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rideDurationApprox Context triple: [E.T. Adventure (Universal Studios Hollywood), rideDurationApprox, 4 minutes]
-
A.
rideDuration
chosen
Indicates the length of time that a ride or trip lasts from start to finish.
-
B.
banDurationApproximate
Indicates that the duration of a ban is known only approximately rather than as an exact, precise time period.
-
C.
hasApproximateWalkingTimeTo
Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
-
D.
rideType
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
-
E.
voyageDuration
Indicates the length of time that a voyage or journey lasts from its start to its end.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84561c7081909e5937c7816e492c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 1:59 p.m.