Triple
T30726283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancer (Fate/Zero) |
E782286
|
entity |
| Predicate | eyeMarking |
P125456
|
FINISHED |
| Object | beauty mark under right eye |
—
|
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: beauty mark under right eye | Statement: [Lancer (Fate/Zero), eyeMarking, beauty mark under right eye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eyeMarking Context triple: [Lancer (Fate/Zero), eyeMarking, beauty mark under right eye]
-
A.
eyeFeatureObserved
Indicates that a specific characteristic or condition of the eye has been detected or recorded through observation.
-
B.
facialMarkings
chosen
Indicates that one entity has distinctive marks, patterns, or features on its face in relation to another entity or context.
-
C.
eyeDecoration
Indicates the presence, type, or style of decorative elements applied around or on the eyes.
-
D.
eyeCharacteristic
Indicates a relationship where an entity possesses a specific attribute, feature, or quality of its eyes.
-
E.
eyeLocation
Indicates the spatial position or placement of an eye relative to a reference object or coordinate system.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c5e18608190b3b2d8dc10023ec8 |
completed | May 2, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:36 p.m.