Triple
T29069967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Mente Maestra |
E735786
|
entity |
| Predicate | featuresCollaborations |
P198435
|
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: [La Mente Maestra, featuresCollaborations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCollaborations Context triple: [La Mente Maestra, featuresCollaborations, yes]
-
A.
featuresCollaboration
chosen
Indicates that one entity includes, showcases, or is characterized by a collaborative effort or partnership with another entity.
-
B.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
C.
collaboratesVia
Indicates that two or more entities work together or coordinate their activities through a specified medium, channel, or intermediary.
-
D.
usesCollaboration
Indicates that one entity employs or relies on collaborative methods, tools, or partnerships with another entity to achieve a shared goal or perform an activity.
-
E.
featuresFamilyCollaboration
Indicates that there is a collaborative relationship or joint involvement between members of a family in a given context or activity.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: April 28, 2026, 10:19 a.m.