Triple
T36640420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PGL(2,7) |
E904567
|
entity |
| Predicate | hasSmallGroupIdentifier |
P124500
|
FINISHED |
| Object | SmallGroup(336, 208) |
—
|
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: SmallGroup(336, 208) | Statement: [PGL(2,7), hasSmallGroupIdentifier, SmallGroup(336, 208)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSmallGroupIdentifier Context triple: [PGL(2,7), hasSmallGroupIdentifier, SmallGroup(336, 208)]
-
A.
identifiesGroup
chosen
Indicates that one entity serves to recognize, label, or distinguish another entity as belonging to a particular group or category.
-
B.
hasSmallerCoreGroup
Indicates that one entity’s core group is smaller in size or membership than another entity’s core group.
-
C.
hasRepresentativeGroup
Indicates that an entity is associated with, or formally represented by, a specific group acting on its behalf.
-
D.
hasCommunicationIdentifier
Indicates that an entity is associated with a specific communication-related identifier (such as a phone number, email address, or messaging handle) used for contact or messaging purposes.
-
E.
hasIdentifierSystem
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.