Triple
T15017195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athirat’s seventy sons |
E377985
|
entity |
| Predicate | collectiveNameRefersTo |
P1519
|
FINISHED |
| Object | offspring of the mother goddess Athirat |
—
|
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: offspring of the mother goddess Athirat | Statement: [Athirat’s seventy sons, collectiveNameRefersTo, offspring of the mother goddess Athirat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveNameRefersTo Context triple: [Athirat’s seventy sons, collectiveNameRefersTo, offspring of the mother goddess Athirat]
-
A.
collectivelyKnownAs
Indicates that multiple entities are referred to together under a single shared name or designation.
-
B.
usedCollectiveName
chosen
Indicates that a group of entities is referred to by a shared collective name.
-
C.
formerCollective
Indicates a relationship where an entity was once part of a collective group or organization but is no longer a member.
-
D.
collectiveBody
Indicates that multiple individuals are grouped and act together as a single collective entity or body.
-
E.
canonicallyReferredToAs
Indicates that one entity is the officially recognized or standard name or label by which another entity is known.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7633fcc8190b2231f43252bc46f |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:55 a.m.