Triple
T5934139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ArcelorMittal |
E132002
|
entity |
| Predicate | headcount |
P10694
|
FINISHED |
| Object | over 150000 employees |
—
|
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 150000 employees | Statement: [ArcelorMittal, headcount, over 150000 employees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headcount Context triple: [ArcelorMittal, headcount, over 150000 employees]
-
A.
hasHeadCount
chosen
Indicates that an entity is associated with a specific number of individuals, typically representing the size or count of people (or similar units) related to it.
-
B.
heads
Indicates that one entity leads, directs, or is in charge of another entity, such as an organization, group, or initiative.
-
C.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
-
D.
headDisplayedBy
Indicates that a particular head (e.g., of a character, avatar, or object) is being visually shown or rendered by a specific display context or system.
-
E.
count
Indicates the numerical quantity or total number of instances of a specified entity or event.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03f26f51881908cc253fe5775a1fc |
completed | March 22, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c03355caf08190b960563a1aed23f9 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.