Triple
T13119830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boomerang Bro |
E311691
|
entity |
| Predicate | projectileTrajectory |
P75831
|
FINISHED |
| Object | arc |
—
|
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: arc | Statement: [Boomerang Bro, projectileTrajectory, arc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectileTrajectory Context triple: [Boomerang Bro, projectileTrajectory, arc]
-
A.
projectileApogee
chosen
Indicates the highest point reached by a projectile along its trajectory before it begins to descend.
-
B.
involvesProjectile
Indicates that the action or event includes the use, presence, or motion of a projectile as a key component of the interaction between entities.
-
C.
meteorVelocity
Indicates the speed and direction at which a meteor is moving through space or an atmosphere.
-
D.
flightScope
Indicates a relationship where the extent, range, or coverage of a flight (such as its route, duration, or operational limits) is specified or constrained.
-
E.
catapultOrigin
Indicates the original source or starting point from which something is launched or propelled, as by a catapult.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98196e69081909111407ee3d9f08e |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.