Triple
T9430993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquamarine |
E227373
|
entity |
| Predicate | streak |
P88862
|
FINISHED |
| Object | white |
—
|
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: white | Statement: [Aquamarine, streak, white]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streak Context triple: [Aquamarine, streak, white]
-
A.
notableStreakMatch
Indicates that a match is part of a significant or noteworthy streak (such as consecutive wins, losses, or performances) associated with an entity.
-
B.
longestUnbeatenStreak
Indicates the relationship where an entity holds the greatest continuous sequence of events (such as games or matches) without a loss compared to others.
-
C.
hittingStreakStartDate
Indicates the date on which a continuous sequence of successful hits (a hitting streak) begins.
-
D.
hittingStreakEndDate
Indicates the date on which a continuous sequence of successful hits or performances comes to an end.
-
E.
hostCityStreak
Indicates a sequence or run of consecutive times a particular city has served as the host for a recurring event.
- F. None of above. chosen
Provenance (4 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e5ed7408190beda5fb078e9345a |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:49 p.m.