Triple
T35790724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tic Tac (UFO) |
E1034684
|
entity |
| Predicate | radarTrackedBy |
P26119
|
FINISHED |
| Object | USS Princeton SPY-1 radar |
—
|
NE NERFINISHED |
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: USS Princeton SPY-1 radar | Statement: [Tic Tac (UFO), radarTrackedBy, USS Princeton SPY-1 radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radarTrackedBy Context triple: [Tic Tac (UFO), radarTrackedBy, USS Princeton SPY-1 radar]
-
A.
isTrackedBy
chosen
Indicates that an entity’s state, behavior, or changes are being monitored, recorded, or followed by another entity.
-
B.
radarConfirmation
Indicates that an observed object, event, or target has been positively detected or verified using radar.
-
C.
associatedRadar
Indicates that one entity is linked or connected to a specific radar system or radar-related resource.
-
D.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
E.
isTracked
Indicates that an entity’s state, behavior, or presence is being monitored or recorded over time.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a22e0ff88190989a5df84fca968b |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.