Triple
T25782276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team Rubicon |
E649320
|
entity |
| Predicate | notableResponseType |
P35851
|
FINISHED |
| Object | hurricanes |
—
|
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: hurricanes | Statement: [Team Rubicon, notableResponseType, hurricanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableResponseType Context triple: [Team Rubicon, notableResponseType, hurricanes]
-
A.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
-
B.
notableTargetType
chosen
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
C.
notableDisplay
Indicates that something is prominently or distinctively presented in a way that draws special attention or recognition.
-
D.
notableContentType
Indicates the type or category of content for which an entity is notable or best known.
-
E.
notableReport
Indicates that an entity has produced, authored, or is otherwise associated with a report that is considered notable or significant.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: April 22, 2026, 5:51 a.m.