Triple
T12250435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lysis |
E291955
|
entity |
| Predicate | hasCentralQuestion |
P4939
|
FINISHED |
| Object | What is a friend? |
—
|
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: What is a friend? | Statement: [Lysis, hasCentralQuestion, What is a friend?]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralQuestion Context triple: [Lysis, hasCentralQuestion, What is a friend?]
-
A.
centralQuestion
Indicates that something is the main issue, problem, or inquiry around which a discussion, work, or investigation is focused.
-
B.
hasKeyQuestion
chosen
Indicates that one entity possesses or is associated with a primary or central question relevant to another entity.
-
C.
hasCentralSection
Indicates that an entity possesses a distinct middle or central part within its overall structure or composition.
-
D.
hasCentralAct
Indicates that an entity includes or is characterized by a primary or most important action, event, or operation at its core.
-
E.
hasCentralTheme
Indicates that one entity serves as the primary or dominant theme or subject matter of another entity.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.