Triple
T7227817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .IXIC |
E154825
|
entity |
| Predicate | includesDomesticCompanies |
P21245
|
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: [.IXIC, includesDomesticCompanies, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDomesticCompanies Context triple: [.IXIC, includesDomesticCompanies, true]
-
A.
includesPrivateCompanies
chosen
Indicates that the relationship or set explicitly encompasses or applies to private companies as part of its scope.
-
B.
includesPublicCompanies
Indicates that the referenced set, group, or collection contains one or more publicly traded companies as members.
-
C.
containsDomesticSpecies
Indicates that one entity includes or encompasses at least one species that has been domesticated by humans.
-
D.
isPrivateCompany
Indicates that an entity operates as a privately held company, not publicly traded on a stock exchange.
-
E.
hadDomesticComponentIn
Indicates that an entity included or involved a domestic (within the same country) component as part of its overall composition, activity, or operation during a specified context or period.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9df72cc81908d1c04e6e310fbb4 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.