Triple
T24662697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bructeri |
E610579
|
entity |
| Predicate | someMembersLaterKnownAs |
P144948
|
FINISHED |
| Object | Chamavi |
E610578
|
NE 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: Chamavi | Statement: [Bructeri, someMembersLaterKnownAs, Chamavi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: someMembersLaterKnownAs Context triple: [Bructeri, someMembersLaterKnownAs, Chamavi]
-
A.
someMembersLater
Indicates that at least some members of a group or set occur, appear, or hold a property at a later time relative to another reference point or group.
-
B.
laterBecameKnownAs
chosen
Indicates that an entity was previously known by one name or identity and, at a later time, came to be known by a different name or identity.
-
C.
laterMember
Indicates that one entity became a member of a group or organization at a later time than another entity.
-
D.
hasLaterMember
Indicates that one member in an ordered sequence occurs later than another member in that same sequence.
-
E.
formerMemberOf
Indicates that an entity once belonged to or was affiliated with a group, organization, or body, but is no longer a member.
- F. None of above.
Provenance (4 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1004a069e48190829fe20e8d460f16 |
completed | May 22, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:34 a.m.