Triple
T27881940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seleucidis |
E705111
|
entity |
| Predicate | courtshipSite |
P7849
|
FINISHED |
| Object | display perches |
—
|
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: display perches | Statement: [Seleucidis, courtshipSite, display perches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtshipSite Context triple: [Seleucidis, courtshipSite, display perches]
-
A.
courtshipMode
Indicates the manner or strategy by which one entity engages in behaviors intended to attract or win the favor of another for a romantic or reproductive relationship.
-
B.
courtships
Indicates that one entity engages in courtship behavior toward another, typically as part of initiating or maintaining a romantic or mating relationship.
-
C.
isSiteOf
chosen
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
D.
betrothalOrMarriagePlace
Indicates the location where a betrothal or marriage event takes place.
-
E.
rendezvousWith
Indicates that two or more entities meet or come together at an agreed place and time, often for a specific purpose.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 6:30 p.m.