Triple
T28616677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FindText |
E724287
|
entity |
| Predicate | notificationCode |
P80191
|
FINISHED |
| Object | FR_FINDNEXT |
—
|
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: FR_FINDNEXT | Statement: [FindText, notificationCode, FR_FINDNEXT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notificationCode Context triple: [FindText, notificationCode, FR_FINDNEXT]
-
A.
notification
Indicates that one entity sends or presents an alert or message to another entity to inform them of some event, change, or required action.
-
B.
notificationType
chosen
Indicates the specific category or kind of notification associated with an event or action.
-
C.
requiresNotification
Indicates that a particular action, event, or state must trigger a notification to be sent to relevant parties.
-
D.
networkCode
Indicates that an entity is associated with, identified by, or operates under a specific network code within a communication or organizational network.
-
E.
notificationDeadline
Indicates the time or date by which a required notification must be sent or received.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:32 a.m.