Triple
T35079148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omexom |
E1012384
|
entity |
| Predicate | hasNumberOfBusinessUnits |
P198176
|
FINISHED |
| Object | over 400 |
—
|
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: over 400 | Statement: [Omexom, hasNumberOfBusinessUnits, over 400]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfBusinessUnits Context triple: [Omexom, hasNumberOfBusinessUnits, over 400]
-
A.
hasNumberOfCompanies
Indicates the quantitative relationship specifying how many companies are associated with a given entity.
-
B.
hasBusinessDivision
Indicates that an organization includes or is composed of a specific business division as a subordinate unit.
-
C.
hasNumberOfAgencies
Indicates the quantity of agencies associated with or linked to a given entity.
-
D.
hasBusinessOperationsIn
Indicates that a business or organization conducts commercial or operational activities within a specified geographic location or jurisdiction.
-
E.
hasSubsidiaryBusiness
Indicates that one business entity owns or controls another business entity as its subsidiary.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
| PDg | Predicate description generation | batch_69feced436a48190b761db7df2d6b6bd |
completed | May 9, 2026, 6:06 a.m. |
Created at: May 3, 2026, 4:01 p.m.