Triple
T10753486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marc-André |
E253629
|
entity |
| Predicate | isWrittenWith |
P95800
|
FINISHED |
| Object | hyphen |
—
|
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: hyphen | Statement: [Marc-André, isWrittenWith, hyphen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWrittenWith Context triple: [Marc-André, isWrittenWith, hyphen]
-
A.
canBeWrittenIn
Indicates that something is capable of being expressed, encoded, or represented using a particular language, notation, or medium.
-
B.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
C.
writingSystemUsedIn
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
-
D.
writingSystemDevelopedFor
Indicates that a particular writing system was created or adapted specifically to be used for a given language, community, or purpose.
-
E.
currentlyWrittenIn
Indicates that a work or document is, at the present time, expressed or composed in a particular language or writing system.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71dc2543c8190bb060aa7a1fed6a6 |
completed | April 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:15 p.m.