Triple
T27560130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MultiMarkdown |
E695747
|
entity |
| Predicate | supportsMetadataKey |
P164341
|
FINISHED |
| Object | Title |
—
|
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: Title | Statement: [MultiMarkdown, supportsMetadataKey, Title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMetadataKey Context triple: [MultiMarkdown, supportsMetadataKey, Title]
-
A.
hasMetadata
Indicates that one entity is associated with descriptive or informational data about another entity.
-
B.
dynamicMetadataSupport
Indicates that the subject system or component is capable of handling metadata that can change or be updated at runtime rather than being fixed or static.
-
C.
isMetadataAttribute
chosen
Indicates that one entity functions as a metadata attribute describing or qualifying another entity.
-
D.
appliesToMetadata
Indicates that something is relevant or specifically directed toward metadata rather than the primary content or data itself.
-
E.
supportsMultipleKeys
Indicates that an entity is capable of handling, accepting, or operating with more than one key simultaneously or in parallel.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: April 27, 2026, 1:38 p.m.