Triple
T30726705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NXPI |
E782295
|
entity |
| Predicate | freeFloatStatus |
P170074
|
FINISHED |
| Object | publicly traded |
—
|
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: publicly traded | Statement: [NXPI, freeFloatStatus, publicly traded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freeFloatStatus Context triple: [NXPI, freeFloatStatus, publicly traded]
-
A.
freeFloatRequirement
Indicates that there is a specified minimum proportion of a security’s shares that must be freely tradable (not closely held) in the market.
-
B.
freeFloatAdjustment
Indicates an adjustment made to account for the portion of shares that are freely tradable (free float), typically modifying a value or metric based on the free-float share base.
-
C.
floatType
Indicates that an entity has a specific floating-point data type or is categorized as a floating-point numeric value.
-
D.
freelyFloating
Indicates that an entity is not fixed or attached to anything and can move or remain suspended without constraint in a surrounding medium.
-
E.
freeFlowing
Indicates that something moves or progresses smoothly and continuously without obstruction or restriction.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c5e18608190b3b2d8dc10023ec8 |
completed | May 2, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:37 p.m.