Triple
T7986062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google MapReduce |
E185683
|
entity |
| Predicate | outputDataModel |
P535
|
FINISHED |
| Object | key-value pairs |
—
|
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: key-value pairs | Statement: [Google MapReduce, outputDataModel, key-value pairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputDataModel Context triple: [Google MapReduce, outputDataModel, key-value pairs]
-
A.
dataModel
chosen
Indicates a relationship where an entity defines, uses, or is structured according to a specific data model or schema.
-
B.
outputOf
Indicates that one entity is the result or product generated by the processing, operation, or behavior of another entity.
-
C.
dataAccessModel
Indicates the framework or scheme that governs how data can be accessed, including who can retrieve it, under what conditions, and through which mechanisms.
-
D.
outputProperty
Indicates that a property or attribute is produced, exposed, or yielded as the output of a process, function, or system.
-
E.
dataControl
Indicates that one entity has the authority or capability to determine how another entity’s data is collected, used, shared, or managed.
- 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c4b87e48190a797f5363c8f0a04 |
completed | March 31, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:15 p.m.