Triple
T28124334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingvaeones |
E710884
|
entity |
| Predicate | traditionalMember |
P156266
|
FINISHED |
| Object | Angles |
—
|
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: Angles | Statement: [Ingvaeones, traditionalMember, Angles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalMember Context triple: [Ingvaeones, traditionalMember, Angles]
-
A.
traditionalMembership
chosen
Indicates that an entity belongs to or participates in a group, organization, or category according to long-established or customary criteria or practices.
-
B.
traditionalMemberRace
Indicates that an entity belongs to a race or ethnic group that is traditionally associated with or historically characteristic of a particular membership or community.
-
C.
traditionalUser
Indicates that a user engages with or is characterized by conventional, established, or customary practices, behaviors, or methods.
-
D.
creditedMember
Indicates that a particular member is formally acknowledged or recognized as having contributed to or been responsible for something.
-
E.
originalMemberClub
Indicates that an entity was one of the initial or founding members of a particular club.
- 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 27, 2026, 9:19 p.m.