Triple
T33863164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLC 2006 |
E867973
|
entity |
| Predicate | partBCharacter |
P177487
|
FINISHED |
| Object | non-mandatory guidelines |
—
|
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: non-mandatory guidelines | Statement: [MLC 2006, partBCharacter, non-mandatory guidelines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partBCharacter Context triple: [MLC 2006, partBCharacter, non-mandatory guidelines]
-
A.
partBType
Indicates that one entity is classified as the type or category to which the second entity (part B) belongs.
-
B.
componentCharacter1
Indicates that one entity is the first (primary) character component or constituent part of another entity.
-
C.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
D.
basedOnCharacterBy
Indicates that one work, adaptation, or portrayal is derived from or inspired by a character created by another entity.
-
E.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f700a00d048190b2af302cc0e982c4 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5a4f7881909324eb3c20ca96f1 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6fcc44af48190b95fb9e12480a85f |
completed | May 3, 2026, 7:44 a.m. |
Created at: May 1, 2026, 1:47 a.m.