Triple
T13103702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern California Logistics Airport |
E310785
|
entity |
| Predicate | hasBasedCompany |
P51457
|
FINISHED |
| Object | aircraft storage companies |
—
|
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: aircraft storage companies | Statement: [Southern California Logistics Airport, hasBasedCompany, aircraft storage companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasedCompany Context triple: [Southern California Logistics Airport, hasBasedCompany, aircraft storage companies]
-
A.
hasFoundedCompany
Indicates that a person or entity has established or created a company.
-
B.
hasCompanyName
Indicates that an entity is associated with or identified by a specific company name.
-
C.
hasAssociatedCompany
chosen
Indicates that one entity is linked or connected to a company in an associated or affiliated manner.
-
D.
hasParentCompany
Indicates that one company is owned or controlled by another company that serves as its parent organization.
-
E.
hasBusiness
Indicates that one entity owns, operates, or is formally associated with a business 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98153255c8190b6ab64ac0c4716f8 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:04 p.m.