Triple
T35249841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ammonites |
E1018065
|
entity |
| Predicate | biblicalEthnonym |
P172821
|
FINISHED |
| Object | Ammon |
—
|
NE NERFINISHED |
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: Ammon | Statement: [Ammonites, biblicalEthnonym, Ammon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalEthnonym Context triple: [Ammonites, biblicalEthnonym, Ammon]
-
A.
hasBiblicalEthnonym
chosen
Indicates that an entity is associated with or identified by an ethnonym (a people or ethnic group name) that originates from or is used within the Bible.
-
B.
ethnonymRoot
Indicates that one term serves as the morphological or etymological root from which an ethnonym (a name for an ethnic group or people) is derived.
-
C.
ethnonym
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
-
D.
biblicalName
Indicates that one entity is the name of a person, place, or concept as it appears in the Bible.
-
E.
ethnonymAttestedIn
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.