Triple
T14020346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linfox |
E337313
|
entity |
| Predicate | isPrivatelyHeld |
P22345
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Linfox, isPrivatelyHeld, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrivatelyHeld Context triple: [Linfox, isPrivatelyHeld, true]
-
A.
isPrivateCompany
chosen
Indicates that an entity operates as a privately held company, not publicly traded on a stock exchange.
-
B.
isPubliclyTraded
Indicates that a company’s shares are listed on a public stock exchange and can be bought and sold by the general investing public.
-
C.
includesPrivateCompanies
Indicates that the relationship or set explicitly encompasses or applies to private companies as part of its scope.
-
D.
isPrivateClub
Indicates that the entity functions as a club or organization that restricts membership or access to a select, non-public group of people.
-
E.
isPrivateOrPublic
Indicates whether something is designated as private or public in terms of its accessibility or visibility.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3c7cd88190b236382058581740 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.