Triple
T27588916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manila API |
E699748
|
entity |
| Predicate | supportsProtocolForShares |
P35980
|
FINISHED |
| Object | NFS |
—
|
NE NERFINISHED |
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: NFS | Statement: [Manila API, supportsProtocolForShares, NFS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProtocolForShares Context triple: [Manila API, supportsProtocolForShares, NFS]
-
A.
supportedProtocol
chosen
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
B.
supportsShares
Indicates that one entity provides assistance, endorsement, or resources to another entity in the context of shared ownership, shared resources, or jointly held interests.
-
C.
allowsShares
Indicates that one entity grants another entity permission to share or distribute something.
-
D.
supportsDataExchange
Indicates that one entity enables or facilitates the transfer or sharing of data with another entity.
-
E.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
Created at: April 27, 2026, 2:05 p.m.