Triple
T2027768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capernaum |
E44447
|
entity |
| Predicate | ancientFunction |
P2715
|
FINISHED |
| Object | fishing village |
—
|
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: fishing village | Statement: [Capernaum, ancientFunction, fishing village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancientFunction Context triple: [Capernaum, ancientFunction, fishing village]
-
A.
historicalFunction
chosen
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
B.
ancientCity
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
-
C.
traditionalFunction
Indicates that an entity serves a customary or historically established role or purpose within a cultural or social context.
-
D.
ancientNameOf
Indicates that one entity is the historical or ancient name by which the other entity was formerly known.
-
E.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb911e5dc819097e40af0da4d01e7 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.