Triple
T4618869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LG |
E100930
|
entity |
| Predicate | memberCountApprox |
P43282
|
FINISHED |
| Object | more than 50 galaxies |
—
|
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: more than 50 galaxies | Statement: [LG, memberCountApprox, more than 50 galaxies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberCountApprox Context triple: [LG, memberCountApprox, more than 50 galaxies]
-
A.
numberOfFullMembers
Indicates the total count of entities that hold full membership status within a specified group or organization.
-
B.
guestCountApproximate
chosen
Indicates that the number of guests involved is represented as an estimated or approximate count rather than an exact figure.
-
C.
staffSize
Indicates the number of staff members associated with an entity.
-
D.
membersPerTribe
Indicates the number of individual members associated with each tribe in the relationship.
-
E.
memberCountAtPeak
Indicates the highest number of members that an entity (such as a group or organization) has had at any point in time.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e247448190ad92f194cb1127c5 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.