Triple
T14669016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Migdal |
E344456
|
entity |
| Predicate | economicActivityInAntiquity |
P110387
|
FINISHED |
| Object | fishing |
—
|
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 | Statement: [Migdal, economicActivityInAntiquity, fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicActivityInAntiquity Context triple: [Migdal, economicActivityInAntiquity, fishing]
-
A.
hasEconomicActivityInAntiquity
chosen
Indicates that an entity engaged in or was associated with economic activities (such as trade, production, or commerce) during ancient historical periods.
-
B.
hasTraditionalEconomyActivity
Indicates that an entity engages in or is associated with economic activities based on traditional practices, customs, or subsistence methods.
-
C.
economicSectorSourceOfWealth
Indicates that a particular economic sector is the primary source from which an entity derives its wealth or income.
-
D.
primaryFunctionInAntiquity
Indicates the main role or purpose an entity served during ancient times.
-
E.
formerEconomicActivity
Indicates that an entity previously engaged in a specified economic activity 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54dda1c8190bf16d17e26a2bba6 |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.