Triple
T5327208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guatemalan Americans |
E123213
|
entity |
| Predicate | commonEmploymentSector |
P62538
|
FINISHED |
| Object | construction |
—
|
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: construction | Statement: [Guatemalan Americans, commonEmploymentSector, construction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonEmploymentSector Context triple: [Guatemalan Americans, commonEmploymentSector, construction]
-
A.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
B.
hasOccupationSector
chosen
Indicates that an entity’s occupation belongs to or is categorized within a particular economic or professional sector.
-
C.
professionalSector
Indicates the industry or field in which an entity conducts its professional or occupational activities.
-
D.
employerType
Indicates the classification or category of an employer in relation to the entity (e.g., public, private, nonprofit, self-employed).
-
E.
typicalEmployer
Indicates that one entity is the kind of organization or person that commonly or usually employs the other 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85926c388190a495835caf927624 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.