Triple
T36987341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farish family |
E914999
|
entity |
| Predicate | associatedWithBusinessSector |
P47145
|
FINISHED |
| Object | energy |
—
|
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: energy | Statement: [Farish family, associatedWithBusinessSector, energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBusinessSector Context triple: [Farish family, associatedWithBusinessSector, energy]
-
A.
associatedWithEconomicSector
chosen
Indicates that an entity has a connection or involvement with a particular economic sector, such as operating, participating, or being relevant within that sector.
-
B.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
C.
hasOccupationSector
Indicates that an entity’s occupation belongs to or is categorized within a particular economic or professional sector.
-
D.
sectoralClassification
Indicates how an entity is categorized into a specific economic or industry sector within a classification scheme.
-
E.
sectoralEngagement
Indicates engagement or involvement between entities within a specific sector or industry context.
- 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.