Triple
T3380696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LAN Airlines (shares) |
E71174
|
entity |
| Predicate | corporateFormOfIssuer |
P30194
|
FINISHED |
| Object | publicly traded company |
—
|
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 company | Statement: [LAN Airlines (shares), corporateFormOfIssuer, publicly traded company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corporateFormOfIssuer Context triple: [LAN Airlines (shares), corporateFormOfIssuer, publicly traded company]
-
A.
hasUnderlyingCompanyLegalForm
chosen
Indicates that an entity is associated with, or governed by, a specific underlying legal form of a company.
-
B.
corporateStructure
Indicates how entities are organized, controlled, and related within a corporate hierarchy or ownership structure.
-
C.
headquartersOfIssuer
Indicates the location that serves as the main headquarters of the issuing entity.
-
D.
organizationTypeOfHolder
Indicates that a specified organization serves as the type or category of the holder in the given relationship.
-
E.
companyIncorporatedIn
Indicates that a company was legally formed and registered in a specified jurisdiction or location.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5e7c7f48190afb78c311b424c93 |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.