Triple
T187778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Generation Partnership Project |
E4019
|
entity |
| Predicate | hasPartnerType |
P781
|
FINISHED |
| Object | organizational partners |
—
|
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: organizational partners | Statement: [3rd Generation Partnership Project, hasPartnerType, organizational partners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartnerType Context triple: [3rd Generation Partnership Project, hasPartnerType, organizational partners]
-
A.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
B.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
C.
hasAffiliationType
chosen
Indicates that one entity is connected to another through a specified kind or category of affiliation or association.
-
D.
hasCommunityType
Indicates that an entity is associated with or classified under a particular type or category of community.
-
E.
hasTypeOfRecipient
Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2594940e48190a3d8efbce46241c3 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25670feb081908e26a2543ebe7b3a |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.