Triple
T26026930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merhav Am |
E647317
|
entity |
| Predicate | socioEconomicType |
P89201
|
FINISHED |
| Object | small community |
—
|
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: small community | Statement: [Merhav Am, socioEconomicType, small community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socioEconomicType Context triple: [Merhav Am, socioEconomicType, small community]
-
A.
socioEconomicBase
Indicates a foundational socio-economic relationship where one entity serves as the economic or social basis, support, or underlying structure for another.
-
B.
socioeconomicRole
chosen
Indicates the social and economic position, function, or status an entity holds within a society or system.
-
C.
economicStatus
Indicates the financial or socioeconomic condition or standing of an entity relative to others or to defined economic criteria.
-
D.
socialClassSystem
Indicates a hierarchical organization of people into social classes based on status, power, or economic position.
-
E.
hasSocioEconomicContext
Indicates the broader social and economic conditions or circumstances within which an entity, event, or relationship occurs or is interpreted.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605ec65448190895219d85eb0d6a8 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:05 a.m.