Triple
T36963713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clockwork Mansion |
E914371
|
entity |
| Predicate | hasMultipleApproaches |
P197499
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Clockwork Mansion, hasMultipleApproaches, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleApproaches Context triple: [Clockwork Mansion, hasMultipleApproaches, yes]
-
A.
approaches
Indicates that one entity moves closer in position or state to another entity or reference point.
-
B.
hasApproachType
Indicates the specific method, strategy, or manner in which an action, process, or interaction is carried out or approached.
-
C.
hasChallengingApproach
Indicates that the approach or method involved in reaching or engaging with something is difficult, complex, or demanding.
-
D.
includesApproach
Indicates that one entity incorporates, utilizes, or is characterized by a particular method, strategy, or approach in relation to another entity or context.
-
E.
hasApproachFeature
Indicates that something possesses a characteristic, element, or quality specifically related to its method, strategy, or manner of approach.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
| PDg | Predicate description generation | batch_69fe96c0b760819093737292d33df165 |
completed | May 9, 2026, 2:06 a.m. |
Created at: May 3, 2026, 4:14 p.m.