Triple
T29721580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarbo |
E752067
|
entity |
| Predicate | alsoInSuiteWith |
P167635
|
FINISHED |
| Object | "Ondine" |
—
|
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: "Ondine" | Statement: [Scarbo, alsoInSuiteWith, "Ondine"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoInSuiteWith Context triple: [Scarbo, alsoInSuiteWith, "Ondine"]
-
A.
alsoIn
Indicates that an entity participates in or belongs to an additional context, group, or location alongside another already specified one.
-
B.
alsoComposedWith
Indicates that something is created or formed together with one or more additional components, highlighting a joint or complementary composition relationship.
-
C.
alsoSitsWith
Indicates that one entity sits together with another entity, sharing the same seating context or location.
-
D.
alsoMetAt
Indicates that the same entities met together at an additional, distinct place or event beyond a previously mentioned meeting location.
-
E.
alsoRunsIn
Indicates that an entity (such as a program, process, or event) operates or occurs in an additional context, environment, or location beyond its primary one.
- F. None of above. chosen
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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672fbd174819094642a594a447e47 |
completed | May 2, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 7:36 p.m.