Triple
T7792488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephyra |
E180213
|
entity |
| Predicate | sometimesConsidered |
P1120
|
FINISHED |
| Object | early name of Corinth |
—
|
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: early name of Corinth | Statement: [Ephyra, sometimesConsidered, early name of Corinth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesConsidered Context triple: [Ephyra, sometimesConsidered, early name of Corinth]
-
A.
couldConsider
Indicates that one entity has the potential or option to take another entity into account when making a decision, judgment, or evaluation.
-
B.
considered
chosen
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
C.
consideredIn
Indicates that one entity is taken into account, examined, or included as a factor within the context, scope, or decision framework of another entity.
-
D.
considersItself
Indicates that an entity regards or perceives itself in a particular way, role, or state.
-
E.
UNConsiders
Indicates that the United Nations is formally examining, deliberating on, or taking into account a particular issue, proposal, or situation.
- 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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:30 p.m.