Triple
T19073109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Third Condition |
E466839
|
entity |
| Predicate | inLanguageCommunity |
P5562
|
FINISHED |
| Object | Hebrew literary 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: Hebrew literary community | Statement: [The Third Condition, inLanguageCommunity, Hebrew literary community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inLanguageCommunity Context triple: [The Third Condition, inLanguageCommunity, Hebrew literary community]
-
A.
hasLanguageCommunity
chosen
Indicates that an entity is associated with or serves a particular language community.
-
B.
linguisticMinorityIn
Indicates that a group or population constitutes a linguistic minority within a specified geographic or political region.
-
C.
hasNeighboringLanguageCommunity
Indicates that one language community is geographically or socially adjacent to another, allowing for direct contact or interaction between them.
-
D.
languageLocalCommunities
Indicates that a language is used, maintained, or holds significance within specific local communities or regions.
-
E.
sharesLanguageWith
Indicates that two entities use at least one common language for communication.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e1ce5881908367424c89d73feb |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.