Triple
T30726703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NXPI |
E782295
|
entity |
| Predicate | reportsOnForm |
P94383
|
FINISHED |
| Object | Form 20-F |
—
|
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: Form 20-F | Statement: [NXPI, reportsOnForm, Form 20-F]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportsOnForm Context triple: [NXPI, reportsOnForm, Form 20-F]
-
A.
reportsFor
Indicates that one entity is subordinate to another and is required to provide updates or answer to that entity, typically within an organizational or hierarchical structure.
-
B.
reportsFormat
chosen
Indicates that one entity reports or presents information in a particular format specified by another entity.
-
C.
reportsFrom
Indicates that one entity provides information, updates, or status reports to another entity, typically reflecting a reporting or accountability relationship.
-
D.
reportsWithin
Indicates that one entity submits or delivers a report to another entity within a specified time frame or boundary.
-
E.
reportsAs
Indicates that one entity formally reports information, status, or results to another entity.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 8:37 p.m.