Triple
T35861870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Licinii (by adoption) |
E1036972
|
entity |
| Predicate | sharesNomenWith |
P15168
|
FINISHED |
| Object | Licinii (by birth) |
—
|
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: Licinii (by birth) | Statement: [Licinii (by adoption), sharesNomenWith, Licinii (by birth)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesNomenWith Context triple: [Licinii (by adoption), sharesNomenWith, Licinii (by birth)]
-
A.
sharesGivenNameWith
Indicates that two entities have the same given (first) name.
-
B.
sharesNameRootWith
Indicates that two entities have names derived from the same linguistic root or base form.
-
C.
sharesNameBy
Indicates that two entities have the same name or label in common.
-
D.
sharesNameWith
chosen
Indicates that two entities have the same name or an identical naming designation.
-
E.
sharesNameTypeWith
Indicates that two entities have the same type or category of name (e.g., both are first names, both are surnames, or both are of the same naming convention).
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00717f539c8190b70dd0e72c6f7d24 |
completed | May 10, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_6a00710278fc81908889afdcf459ff01 |
completed | May 10, 2026, 11:50 a.m. |
Created at: May 3, 2026, 4:06 p.m.