Triple
T26032661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raccoon Mario |
E647474
|
entity |
| Predicate | hasFlightLimit |
P99
|
FINISHED |
| Object | Timed flight duration |
—
|
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: Timed flight duration | Statement: [Raccoon Mario, hasFlightLimit, Timed flight duration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlightLimit Context triple: [Raccoon Mario, hasFlightLimit, Timed flight duration]
-
A.
hasLockFlight
Indicates that one entity is associated with a specific lock flight, representing a relationship where the entity uses, contains, or is located at that sequence of canal locks.
-
B.
numberOfCaptiveFlights
Indicates the number of flights during which an entity is held or transported in captivity.
-
C.
quantityFlown
Indicates the amount or volume that has been transported by flying from one place to another.
-
D.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
E.
hasScheduledFlights
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 9:06 a.m.